In Azure, different API versions of a resource can have different properties and values.
Using a variable or parameter for the apiVersion for a resource is not an optimal way to always stay up to date with the latest
version. This can lead to unexpected behaviors like deployment failures, when the API version you set for a resource doesn’t match the properties in
your template.
